SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 59458: Errors occur when you try to load Meta Integration Model (MITI) bridges to the relationship database

DetailsHotfixAboutRate It

MITI bridges cannot be loaded into the relationship database when Secure Sockets Layer (SSL) is enabled. This problem occurs because, during the loading, the bridge from a third-party source tries to connect by using the HTTP protocol instead of the HTTPS protocol.

The problem occurs when you submit a command similar to the following:

"C:\ProgramFiles\SASHome\SASMetadataBridges\4.1\tools\sas-metabridge-relationship-loader.exe" -loadRelationships -bridgeIdentifier InformaticaPowerCenter -bridgeOptions "D:\SAS\Test\SAS_Metadata\data\out\02_bridgeIdentifier_InformaticaPowerCenter.xml" -log "D:\SAS\Test\SAS_Metadata\log\04_loadRelationships_20160728_173452.log"-debug -host your-company.net -port 8343 -protocol HTTPS -user "sasadm@saspw" -password "{SAS002}your-password" -bridgeDirectory "C:\Program Files\SASHome\SASMetadataBridges\4.1"

When this problem happens, errors similar to the following are generated:

Error 1

WARN (org.springframework.web.client.RestTemplate) POST request for "http://yourcompany.net:8343/SASWIPClientAccess/rest/relsvc/relationships" resulted in 400 (Bad Request); invoking error handler

Error 2

Bad Request : Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please.

This problem occurs because the HTTP protocol is hardcoded into the underlying code. Instead, the code should use the HTTPS protocol that is passed in the example command shown previously.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Metadata ServerHP-UX IPF9.4_M39.4_M49.4 TS1M39.4 TS1M4
64-bit Enabled Solaris9.4_M39.4_M49.4 TS1M39.4 TS1M4
64-bit Enabled AIX9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Ultimate x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Ultimate 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Professional x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Professional 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Home Premium x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Home Premium 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Enterprise x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Enterprise 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 Std9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 R2 Std9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 R2 Datacenter9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 Datacenter9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2008 for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2008 R29.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 20089.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 109.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Pro x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Pro 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Enterprise x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Enterprise 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Pro x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Pro 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Enterprise x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Enterprise 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft® Windows® for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
z/OS9.4_M39.4_M49.4 TS1M39.4 TS1M4
Linux for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Solaris for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.